Non Functional Requirements
Non Functional
The following table is a list of the non functional requirements for the service.
info
These are based on the assumptions provided in the [[Security System Brief]] briefing.
| Req | Description | Category |
|---|---|---|
| NFR1 | Security: The system should ensure the confidentiality, integrity, and availability of sensitive information. | Must |
| NFR2 | Reliability: The system should operate reliably and consistently, with minimal downtime or errors. | Must |
| NFR3 | Usability: The system should be easy to use for users, administrators, and IT personnel. | Must |
| NFR4 | Performance: The system should be able to process access requests quickly and efficiently. | Must |
| NFR5 | Power Requirements: The system should have a suitable power supply and battery backup in case of power outages. | Must |
| NFR6 | Environmental Resistance: The system should be resistant to environmental factors such as temperature, humidity, and vibration. | Must |
| NFR7 | Compliance: The system should comply with relevant security standards and regulations (e.g., GDPR, HIPAA). | Must |
| NFR8 | Maintenance: The system should be easy to maintain and repair, with minimal technical expertise required. | Should |
| NFR9 | Cost-Effectiveness: The system should provide good value for money, considering the cost of implementation, maintenance, and upgrades. | Should |
| NFR10 | Interoperability: The system should be able to integrate with other security systems and devices from different manufacturers. | Should |
| NFR11 | Scalable: The system should allow for expansion onsite for additional security components. | Must |
| NFR12 | Security Standards: The system should use recognised industry standards for cards and data encryption. These include and not limited to: - MIFARE Classic - MIFARE DESFire EV1/EV2 - ISO 14443A, 14443B, 15693 | Must |